comment
authorJoey Hess <joeyh@joeyh.name>
Tue, 23 May 2023 16:00:01 +0000 (12:00 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 23 May 2023 16:00:01 +0000 (12:00 -0400)
doc/bugs/views_do_use_utf8_for_chars_that_does_not_need_to/comment_1_a6014d95b0ac0dc20e9495a717d6d615._comment [new file with mode: 0644]

diff --git a/doc/bugs/views_do_use_utf8_for_chars_that_does_not_need_to/comment_1_a6014d95b0ac0dc20e9495a717d6d615._comment b/doc/bugs/views_do_use_utf8_for_chars_that_does_not_need_to/comment_1_a6014d95b0ac0dc20e9495a717d6d615._comment
new file mode 100644 (file)
index 0000000..f025d1b
--- /dev/null
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2023-05-23T15:50:51Z"
+ content="""
+The character is actually `﹕`
+
+That is used in views because on windows colon is a special character
+and putting it in the name of a viewed file would prevent checking out the
+view.
+
+It would be possible to skip that on linux, but note that it also 
+escapes `/` on linux with a unicode equivilant (for similar reasons).
+
+Also, the linux executable can sometimes be run on a windows system through
+WSL. I'm not sure how a `:` in a filename would be handled in that situation.
+"""]]